Skip to content

feat: update schema version to v1.7.0#48

Merged
G-Rath merged 2 commits into
mainfrom
update-osv-version
May 26, 2025
Merged

feat: update schema version to v1.7.0#48
G-Rath merged 2 commits into
mainfrom
update-osv-version

Conversation

@G-Rath

@G-Rath G-Rath commented May 22, 2025

Copy link
Copy Markdown
Collaborator

We're actually already using features from later versions than v1.3.0 🤷

@Unifex Unifex left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

Are there really no actual schema changes between 1.3.0 and 1.7.0? I would have expected to see something change in the format of the advisory.

Testing the files against the schema here shows all is good though.

@G-Rath

G-Rath commented May 25, 2025

Copy link
Copy Markdown
Collaborator Author

Are there really no actual schema changes between 1.3.0 and 1.7.0? I would have expected to see something change in the format of the advisory.

The version is semantic, so any breaking changes that'd require us to change would be in a v2 - the changes in these minors are primarily additions of new enum and type-based stuff like prefixes, ecosystems, and severity formats (e.g. CVSS v4.0) ; I'm pretty sure the main new feature is the last_affected event type 🤷

(fwiw too the schema repo is also home to a few auxiliary stuff like binding libraries for Go and tools, which are versioned as well - so it's a little messy to say exactly what changed about the schema specifically 😅)

@G-Rath G-Rath merged commit 277ab28 into main May 26, 2025
5 checks passed
@G-Rath G-Rath deleted the update-osv-version branch May 26, 2025 00:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants